…xt from the schema

Emit the live instrumentation surface alongside the record/event types. Per
entity: an `EntityEvent` impl (stream name = the entity's snake-case name), a
cloneable `{Entity}Observer` factory, and a `{Entity}Handle` with one emit
method per event. Once-cardinality events take `&mut self` and are guarded by
a per-handle `u64` flag word (at most 64 per entity, else
`GenerateError::TooManyOnceEvents`); multi-events take `&self`. A
`{Schema}Context` builds every observer on construction and hands out cheap
`Arc` clones via `{entity}_observer()`. The generator lives under
`src/runtime/`, split into context/observer/handle.

Refine the runtime `Handle` to match the generated calls: `new()` mints a
fresh id, `with_id()` adopts a caller-supplied one, and the once-flag word is
a `u64`.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…amed crate

`cargo bench -p quent-instrumentation` no longer resolves after the
`quent-instrumentation` → `quent-instrumentation-runtime` rename; update the
three invocations to the new package name.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…ld-handle

…ld-handle

# Conflicts:
#	Cargo.lock

…ld-handle

…text's ModelInfo

rapidsai#261 added `ModelInfo::analyzer_package`. The schema-driven path declares no
analyzer entry, so the generated `{Schema}Context::model_info()` sets it to
`None`, keeping the generated crate compiling after the merge.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…-exporter demo

Make a generated instrumentation library reference its backing crate as the
single required dependency, with `quent-exporter` the one exception (so a
consumer can select exporter features):

- Re-export from the runtime everything the generated code references — `Uuid`,
  `CustomAttributes`, `Event`/`EntityEvent`, `EntityRef`, `ObserverError`,
  `build_info` — and route generated field/method types through it
  (`::quent_instrumentation::Uuid`, `::CustomAttributes`). The generated file
  re-exports the data types, so a consumer needs no direct `uuid`/`attributes`
  dependency.
- Source `ExporterOptions` from `quent-exporter` rather than the runtime; the
  generated context's `try_new` takes `::quent_exporter::ExporterOptions`.
- Example: construct the context with a callback exporter that debug-prints
  events, factored into a `debug_printing_exporter()` helper.

Also rename the backing crate `quent-instrumentation-runtime` back to
`quent-instrumentation`, pairing with `quent-instrumentation-build`; the
generated code emits `::quent_instrumentation::…` accordingly.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

…s to the impls

The `Exporter<T>` and `Importer<T>` traits no longer require `T: Serialize` /
`T: Deserialize`. Serialization is an exporter-implementation concern, so the
bound now lives only on the concrete exporters/importers that actually
(de)serialize (ndjson/msgpack/postcard/collector, which already declared it).
`CallbackExporter` type-erases its events, so it drops the bound and becomes a
genuine non-serializing exporter. The runtime's `Observer<T>`/`Handle<T>` drop
the bound too — they only forward events onto a channel; `Context::observer()`
keeps it, since it constructs the exporter.

Also fix the instrumentation-build module docs: the example used a nonexistent
`GenerateOptions` (the type is `Options`) and derives without `Serialize`.
Document that building an exporter requires the event/record types to be
`Serialize`.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>